@Patrick-Campbell Do I understand correctly that you're trying to set up your Omega so that the end-user will see this setup wizard again? If so, we mention how to re-enable the setup wizard in the getting started with OnionOS article: This final step updates the Omega’s configuration to indicate that the first time setup has been completed. Afterwards, when you navigate to your Omega’s address, you’ll see OnionOS. If you ever feel like going through the Setup Wizard again, run uci set onion.console.setup='0' ; uci commit onion on your Omega’s command line and the Setup Wizard will be back.

@Bartosz-Grabias I understand, but is it also possible to reach the OnionOS that way?, and can I program the device via the Code Editor if it is not connected to another network? Thanks !

@Lazar-Demin thanks for your swift answer. Unfortunately the update command does not work: Downloading https://repo.onion.io/omega2/packages/core/Packages.gz *** Failed to download the package list from https://repo.onion.io/omega2/packages/core/Packages.gz both http and https don't work EDIT : Nevermind, I've found the root of my problem, the omega2 does not seem to like network SSIDs that contain special characters. I changed my network's SSID and now all is fine. Thanks for your help

@Chun-Wai-Yuan it could be several different issues which keep the omega2 from connecting. there are many posts in the forum already that discuss methods to correct this problem. if you enter "can not connect to wifi" or "unable to connect to wifi" in the search box in the upper right you will find some probable solutions others have found to work.

Sorry. I did not see this: Restoring after a factory reset. Solved

@WereCatf I assume you mean Power Dock or? Nevertheless, I'm not sure what happened but suddenly today Setup Wizard started to work. Now I'm working on WiFi configuration.

Hello Robert, I experienced the same issue with my initial startup (I caused a couple) ;). I found that holding the reset button and powering on the device once made the AP active and boot seemed normal after that point. The LED on my O2+ didn't act as indicated. However, after a non-conventional firmware upgrade, I was able to see normal LED activity. I've noted that power supplied to the O2+ is definitely a big issue. My laptop can power just the Omega but, anything else (usb accessory or charge battery via Power Dock) it can't. In fact I've found only one power adapter in my house that can do-it-all and it's rated 5 volt 1.6 amp. I understand the frustration but, I see it as a challenge. Where else do you see a $9 computer carrying you without a little mud on the tires? I'm not certain which docks or expansions you have. Any additional info you can provide would be helpful.

@Mitch-Christensen We were doing some maintenance of the firmware servers yesterday in preparation for the Omega2, I'm guessing that caused your issues! Should be ok from here on out! Can you please add [RESOLVED] to the post title?

Hi John, Just read carefully, it says wait till the Omega led stops blinking. After downloading the Firmware it will be copied on the right place and the Omega is starting again. The led will switch of and switch on again and blink till firmware is ready in the Memory. It could be that the Omega not gets online automatically after update. But in this case you can connect it with USB over serial. A how to, you find in omega.io/getstarted With wifi you start the wifi Adapter and with wifisetup you can choose the right wifi network again. As you can store more than one wifi-network, it will be probably deactivated after update.